Avoid Creation of Duplicate Guest Profiles in Stay
Stay is enhanced to prevent the creation of duplicate guest profiles when processing the reservation creation and modification requests sent from Pegasus CRS by validating the patron ID associated with the guest profile details received in the requests with the Casino Management System (CMS) integrated with the property.
Previously, the patron IDs were not validated, which led to the creation of duplicate profiles in Stay.
Patron ID Validation
The patron ID is now validated in the following scenarios before a new guest profile is created:
Sample Scenario 1
|
Details in Stay |
Details Received from Pegasus CRS |
|---|---|
|
James Smith |
James Smith |
|
12345 |
12345 |
Consider a guest profile, James Smith, with patron ID, 12345, sent to Stay from Pegasus. When the profile exists in Stay with the same first name, last name, email address, and contact number details, the patron ID received in the request is validated with the CMS integrated with the property. Since the details match, a new guest profile is not created.
Sample Scenario 2
|
Details in Stay |
Details Received from Pegasus CRS |
|---|---|
|
James Smith |
James Smith |
|
Player ID not available |
12345 |
Consider a guest profile, James Smith, available in Stay without a patron ID. When a profile, James Smith, with patron ID, 12345, is sent to Stay from Pegasus, patron ID received in the request is validated with the CMS integrated with the property. Since the first name, last name, email address, and contact number details match, the patron ID is updated in the profile in Stay, and a new guest profile is not created.
Sample Scenario 3
|
Details in Stay |
Details Received from Pegasus CRS |
|---|---|
|
James Smith |
James Smith |
|
12345 |
Player ID not available |
Consider a guest profile, James Smith, with patron ID, 12345, available in Stay. When a profile, James Smith, without a patron ID is sent to Stay from Pegasus, the patron ID available for the profile in Stay is validated with the CMS integrated with the property. Since the first name, last name, email address, and contact number details match, the patron ID is retained, and a new guest profile is not created.
Sample Scenario 4
|
Details in Stay |
Details Received from Pegasus CRS |
|---|---|
|
James Smith |
James Smith |
|
12345 |
67891 |
Consider a guest profile, James Smith, with patron ID, 12345, available in Stay. When a profile, James Smith, with a different patron ID is received from Pegasus, the patron ID is validated with the CMS integrated with the property. Since the patron ID is different, a new guest profile is created in Stay.
Sample Scenario 5
|
Details in Stay |
Details Received from Pegasus CRS |
|---|---|
|
James Smith |
Nick Jones |
|
12345 |
12345 |
Consider a guest profile, James Smith, with patron ID, 12345, available in Stay. When a profile, Nick Jones, with the same patron ID is received from Pegasus, the patron ID is validated with the CMS integrated with the property, and the first and last names received from Pegasus will be overridden in the guest profile in Stay.
Validation of Other Details
When a patron ID is not available for a profile in Stay and not included in the request sent from Pegasus, the other details which include, name, phone number, and email address are validated.
Sample Scenario 6
|
Details in Stay |
Details Received from Pegasus CRS |
|---|---|
|
James Smith |
James Smith |
In this scenario, since the first and last names of the profile match, the email address marked as Primary in Pegasus will be updated for the profile in Stay and a new guest profile will not be created.
Sample Scenario 7
|
Details in Stay |
Details Received from Pegasus CRS |
|---|---|
|
James Smith |
James Smith |
|
1234567892 |
9087654322 |
|
9087654322 |
5678901234 |
In this scenario, since the first and last names of the profile match, the phone number marked as Primary in Pegasus will be updated for the profile in Stay and a new guest profile will not be created.